AltaPay SalesForce CC Plugin Component overview

Functional overview

The idea of the payment gateway is to allow your customers to perform secure payments without the feeling that they are leaving your web shop. This is possible because AltaPay proxy the payment page from your website – keeping layout and visual identity. The AltaPay Payment Gateway will inject a payment form into the payment page, which reflects the payment method (Credit Card, Bank Payment, etc.).

Use case

The below described use case covers the scenarios a merchant, customer and AltaPay experience when making a payment.

Actors

• Customer: The buyer and payer of items at the web shop
• Merchant: Provides the web shop and items to be sold
• AltaPay: Processes payment information and verifies payment information provided by the customer with help from an acquirer

General payment flow

1. The customer visits the merchant’s web shop and add items to the basket
2. Customer is ready to pay and select preferred payment method
3. Customer is redirected to AltaPay where he enters required payment details (Card number with/without 3D secure, PayPal account etc.)
4. Payment details are sent to AltaPay where they are processed with the relevant acquirer
5. After processing the customer returns to the web shop, where they are informed about the outcome

Card payment flow

1. Customer select card as payment method
2. Customer is presented with the payment page where card details can be typed
3. If the card is enrolled for 3D Secure - the card issuer’s bank present a page where the customer provides their 3D Secure information
   1. if the 3D Secure details are correct and the issuer approves the transaction, the payment is complete. The customer is informed and the merchant can process the order.
   2. in case the 3D Secure details are incorrect or the issuer declines the transaction for other reasons, the customer is redirected to the basket and requested to select payment method again.

Alternative payment flow

1. Customer select an alternative payment method

2. The customer is redirected to the alternative payment provider and will be requested to login. After the customer has logged in, he must accept the pending payment.

3. When the payment has been accepted, the customer is redirected back to the merchant’s web shop where the customer is informed that the payment is complete, and the merchant is able to process the order.

   If the payment could not be verified, but has not been rejected, the payment ends in a status called open (e.g. due to the provider performing a manual fraud review).

   Here the customer is also shown a confirmation page but with a notice that the payment has not been confirmed. The merchant will also be able to see this, as the order has the confirmation status: ‘Not confirmed’.

   If the payment is declined after verification, the status of the order will change to ‘Cancelled’. If the payment is confirmed, the status of the order will change to ‘Confirmed’.

Limitations & Constraints

• The merchant will need a AltaPay test/production terminal
• The merchant must implement their own look and feel on the payment page - otherwise a standard page is shown
• Alternative payments which cannot be preauthorized is shown as cancelled, instead of failed
• For asynchronous payments, which are completed as a successful or declined status at a later stage, the merchant is responsible to notify the customer

Compatibility

Based on Salesforce and SiteGenesis: 17.1 (compatibility mode: 16.2)

Tested on Salesforce and SiteGenesis: 103.1.5

Privacy & Payment

Information about payment method, debit/credit card data, items, shipping/billing addresses and amount is sent to AltaPay.